Attribution issue

• issueId: issue_mo8z05x3_aa5gtw
• category: tool
• canonicalTitle: MCP工具错误提示不清晰导致云函数创建失败
• representativeRun: atomic-js-cloudbase-mock-jinguyuan-dumpling-mcp/2026-04-21T18-40-58-elqzbn

Automation summary

• root_cause: When the CloudBase API returns "400 invalid parameter value" error, the MCP tool's error message was too generic and didn't provide actionable guidance about what parameter was invalid or how to fix it.
• changes: Added error handling for "400 invalid parameter value" errors in mcp/src/tools/functions.ts (lines 404-426). When this error occurs, the function now provides specific suggestions about:

1. Function name format requirements (alphanumeric, underscore, hyphen; max 60 chars)
2. Runtime must be a supported version (e.g., Nodejs20.19, Nodejs18.15, Python3.9)
3. Handler format requirements (for Node.js: filename.exportFunctionName like index.main)
4. Timeout value must be between 1-300 seconds

• validation:
• All 9 existing unit tests in functions.test.ts pass
• All 3 skill/doc regression tests pass (build-skills-repo.test.js, build-compat-config.test.js, skill-quality-standards.test.js)
• follow_up: None. The fix is complete and addresses the attribution issue about unclear MCP tool error messages causing cloud function creation failures.

Changed files

• mcp/src/tools/functions.ts